-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fuzz: drop workarounds for operations that may panic #92
Conversation
…itz compares panic behavior
Oh , it's finding some mismatches in ArrayVec now! Interesting! |
LGTM. 👍 |
ArrayVec panic is pointing to an integer overflow on this line: Line 28 in 5758549
Operation triggering it: I am surprised that this panic is possible to detect in this setup at all. Does this mean that Side note: https://github.com/jakubadamw/rutenspitz/blob/master/DEBUGGING.md is complicated, lldb-specific (no gdb) and possibly requires rust-lldb as opposed to mainline. I've just added a |
Yep, |
The same overflow was also discovered in TinyVec: Line 433 in 5758549
|
CI is failing with DNS resolution errors. |
I used a regular lldb ( |
That sounds worthy of an upstream bug report, silently failing to drain the vector 😦 |
Hmm, building with
so, the behaviour here is actually identical, except |
I've opened an issue against libstd: rust-lang/rust#74909 |
No further failures after 500 million executions of arrayish target and 125 million executions of tinyvec target |
Drop workarounds for operations that may panic now that rutenspitz compares panic behavior
cc @jakubadamw